Course Registration System
Use-Case Specification
Close Registration Use Case
Version 2.0
Revision History
Date |
Version |
Description |
Author |
21/Dec/98 |
Draft |
Draft |
S. Gamble |
13/Feb/99 |
Version 1.0 |
Minor corrections based on
review |
S. Gamble |
15/Feb/99 |
Version 2.0 |
Modify section on use case
extends. Final cleanup. Revise alternative flows. Resolve outstanding
issues. |
S. Gamble |
|
|
|
|
Table of Contents
- Brief Description
- Flow of Events
- Basic Flow – Successful
Close Registration
- Alternative Flows
- Less Than Three Students
in the Course Offering
- No Professor for the
Course Offering
- Billing System Unavailable
- Special Requirements
- Pre-Conditions
- Login
- Post-Conditions
- Extension Points
Close Registration Use Case
- Brief Description
This use case allows a Registrar to close the registration process. Course
offerings that do not have enough students are cancelled. Course offerings must
have a minimum of three students in them. The billing system is notified for
each student in each course offering that is not cancelled, so the student can
be billed for the course offering.
The main actor of this use case is the Registrar. The Billing System is an
actor involved within this use case.
Flow
of Events
The use case begins when the Registrar selects the "close
registration" activity from the Main Form.
Basic
Flow – Successful Close Registration
The system checks to see if a Registration is in progress. If it is, then a
message is displayed to the Registrar and the use case terminates. The Close
Registration processing cannot be performed if registration is in progress. .
For each open course offering, the system checks if three students have
registered and a professor has signed up to teach the course offering. If so,
the system closes the course offering and sends a transaction to the billing
system for each student enrolled in the course offering.
Alternate Flows
- Less Than
Three Students in the Course Offering
If in the basic flow less than three students signed up for the course
offering, the system will cancel the course offering. The Cancel Course
Offering sub-flow is executed at this point.
- Cancel Course Offering
The system cancels the course offering. For each student enrolled in
the cancelled course offering, system will modify the student’s
schedule. The first available alternate course selection will be
substituted for the cancelled course offering. If no alternates are
available, then no substitution will be made. Control returns to the Main
flow to process the next course offering for the semester.
Once all schedules have been processed for the current semester, the
system will notify all students, by mail, of any changes to their schedule
(e.g., cancellation or substitution).
- No Professor
for the Course Offering
If in the basic flow there is no professor signed up to teach the
course offering, the system will cancel the course offering. The Cancel
Course Offering sub-flow is executed at this point.
- Billing System
Unavailable
If the system is unable to communicate with the Billing System, the
system will attempt to re-send the request after a specified period. The
system will continue to attempt to re-send until the Billing System
becomes available
3.
Special Requirements
There are no special requirements associated with this use case.
4.
Pre-Conditions
- Login
The Registrar must be logged onto the system in order for this use case
to begin.
5. Post-Conditions
There are no post-conditions associated with this use case.
6. Extension Points
There are no extension points associated with this use case.
Copyright
© 1987 - 2000 Rational Software Corporation
|